Disk array system and method of controlling disk array system

ABSTRACT

A disk array system having first and second housings and a controller for controlling the first and second housings. Fiber channel hard disk drives are received in the first housing, and serial ATA hard disk drives are received in the second housing. When reading data stored in a serial ATA hard disk drive in the second housing, the controller reads a plurality of pieces of data including the data to be read and parity data for the plurality of pieces of data from all the hard disk drives of an RAID group to which the hard disk drive storing the data to be read belongs. Thus, the controller examines whether the plurality of pieces of data including the data to be read are written in the hard disk drives with erroneous contents or not.

The present application is a continuation of application Ser. No. 10/766,015, filed Jan. 29, 2004, the contents of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

The present invention relates to a disk array system and a method for controlling a disk array system.

In recent years, with the increase of storage capacity in disk array systems, the importance thereof in information processing systems becomes greater and greater. It is therefore essential to write data correctly in a requested position and detect falseness in read data in response to a data input/output request from an information processing apparatus or the like.

JP-A-5-150909 discloses a method in which two heads are provided in a magnetic disk unit, and identical data read from the two heads are compared with each other so as to enhance the reliability in writing and reading in the magnetic disk unit.

When the method disclosed in JP-A-5-150909 is applied to a disk array system, two heads have to be provided in each magnetic disk unit. Thus, the unit cost for manufacturing each hard disk drive increases. Therefore, requested is a method for enhancing the reliability in a hard disk drive without changing its physical structure, for example, without adding any head thereto.

In addition, in disk array systems, serial ATA or parallel ATA hard disk drives have come to be used as well as fiber channel hard disk drives. This is because serial ATA or parallel ATA hard disk drives are indeed inferior in reliability to fiber channel hard disk drives but lower in price. There is therefore a demand for development of a method for enhancing the reliability in hard disk drives other than fiber channel ones in a disk array system constituted by a combination of fiber channel hard disk drives and other hard disk drives conforming to the serial ATA standard or the like.

SUMMARY OF THE INVENTION

The present invention was developed in consideration of the foregoing problems. It is an object of the invention to provide a disk array system and a method for controlling a disk array system.

In order to attain the foregoing object, a disk array system according to a principal configuration of the invention includes a first housing, a second housing and a controller. The first housing stores one or plural RAID groups. Each RAID group is formed out of a plurality of hard disk drives for transmitting/receiving data in accordance with a first interface standard. The hard disk drives are connected through a communication path. The second housing stores one or plural RAID groups. Each RAID group is formed out of a plurality of hard disk drives for transmitting/receiving data in accordance with a second interface standard. The hard disk drives are connected through the communication path via a plurality of converting units for converting the first and second interface standards into each other. The hard disk drives conforming to the second interface standard are lower in reliability than the hard disk drives conforming to the first interface standard. The controller includes a channel control portion, a disk control portion, a cache memory and a CPU. The channel control portion is connected to an information processing apparatus so as to be able to establish communication therewith. The channel control portion receives requests from the information processing apparatus. The requests include a read request to read data from the hard disk drives in the first or second housing and a write request to write data into the hard disk drives in the first or second housing. The disk control portion is connected to the plurality of hard disk drives in the first and second housings through the communication path so as to be able to establish communication with the plurality of hard disk drives in the first and second housings. The disk control portion performs input/output of data and parity data from/to the plurality of hard disk drives in the first and second housings in accordance with the read request or the write request received by the channel control portion. The parity data is data for detecting errors over a plurality of pieces of data including the data from/to the plurality of hard disk drives in the first and second housings. The cache memory temporarily stores data to be written into the plurality of hard disk drives. The CPU administers control over the channel control portion and the disk control portion. The controller reads a plurality of pieces of data including data stored in the plurality of hard disk drives in the second housing and parity data for the plurality of pieces of data, from all of the hard disk drives of the RAID group to which the hard disk drives storing the data belong, and examines whether the plurality of pieces of data including the data have been written in the hard disk drives with erroneous contents or not.

In addition, when writing data into one of the hard disk drives in the second housing in accordance with the write request from the information processing apparatus, the controller moves a head belonging to the hard disk drive from a position where the data has been stored. After that, the controller reads the data from a magnetic disk belonging to the hard disk drive and from the cache memory, and compares the two pieces of data read out.

In addition, when receiving, from the information processing apparatus, the write request to write data into one of the hard disk drives in the second housing, the controller forms a data unit out of data constituted by a plurality of sectors based on the data to be written and parity data for detecting data errors in the plurality of sectors, and writes the data unit into the hard disk drive. When receiving the read request to read the data from the information processing apparatus, the controller reads the data unit and examines whether the data is stored in the hard disk drive with erroneous contents or not.

Here, the first interface standard is, for example, a fiber channel standard. The second interface standard is, for example, a serial ATA standard. The communication path is, for example, an FC-AL (Fiber Channel-Arbitrated Loop). In addition, each converting unit is, for example, a converter for converting a fiber channel protocol and a serial ATA protocol into each other. In addition, each RAID group is to manage a plurality of hard disk drives as one group when the hard disk drives have an RAID configuration. Logical volumes serving as access units from the information processing apparatus are formed on each RAID group. An identifier referred to as LUN is assigned to each logical volume. When receiving from the information processing apparatus a write request to write data into a logical volume, the disk control portion writes the data and parity data for detecting errors in the data, into the hard disk drives forming the RAID group.

Thus, a disk array system and a method for controlling a disk array system can be provided according to the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The problems disclosed in this specification and solutions thereto will become more apparent from the following Detailed Description of Preferred Embodiments in conjunction with the accompanying drawings wherein:

FIGS. 1A and 1B are diagrams showing the appearance of a disk array system according to an embodiment of the invention;

FIGS. 2A and 2B are diagrams showing the configuration of a master housing of the disk array system according to the embodiment;

FIGS. 3A and 3B are diagrams showing the configuration of an expansion housing of the disk array system according to the embodiment;

FIG. 4 is a diagram showing the configuration of a hard disk drive according to the embodiment;

FIG. 5 is a diagram showing the configuration of the disk array system according to the embodiment;

FIG. 6 is a diagram showing the state where microprograms to be executed by a CPU of a controller have been stored in a memory according to the embodiment;

FIG. 7 is a diagram showing a mode for connecting fiber channel hard disk drives to a disk control portion of the controller according to the embodiment;

FIG. 8 is a diagram showing a first mode for connecting serial ATA hard disk drives to the disk control portion of the controller according to the embodiment;

FIG. 9 is a diagram showing a second mode for connecting the serial ATA hard disk drives to the disk control portion of the controller according to the embodiment;

FIG. 10 is a diagram showing an example in which data are written in hard disk drives forming an RAID group according to the embodiment;

FIG. 11 is a diagram showing an update control table according to the embodiment;

FIG. 12 is a flow chart for comparing data stored in a cache memory with data stored in a magnetic disk when data is written according to the embodiment;

FIG. 13 is a flow chart for comparing data stored in a cache memory with data stored in a magnetic disk in consideration of the data size when data is written according to the embodiment;

FIG. 14 is a flow chart for comparing data stored in a cache memory with data stored in a magnetic disk when the data stored in the cache memory is written into the magnetic disk according to the embodiment;

FIG. 15 is a diagram showing a head check control table according to the embodiment;

FIG. 16 is a flow chart for head check to be performed periodically according to the embodiment;

FIG. 17 is a flow chart for carrying out the head check when data is read according to the embodiment;

FIG. 18 is a diagram showing an example in which a data unit has been written in a hard disk drive according to the embodiment;

FIG. 19 is a diagram showing an example in which each data unit has been written and distributed over a plurality of disk drives according to the embodiment;

FIG. 20 is a diagram showing a data unit control table according to the embodiment; and

FIG. 21 is a diagram showing the configuration of the disk array system in which fiber channel hard disk drives are stored in a first housing and serial ATA hard disk drives are stored in a second housing according to the embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS

System Configuration

FIG. 1A is a front view of a disk array system 10 which will be described as an embodiment of the invention. FIG. 1B is a back view of the disk array system 10. FIG. 2A is a perspective view of a master housing 20 to be mounted on the disk array system 10, the master housing 20 being viewed from its front side. FIG. 2B is a perspective view of the master housing 20 viewed from its back side. FIG. 3A is a perspective view of an expansion housing 30 to be mounted on the disk array system 10, the expansion housing 30 being viewed from its front side. FIG. 3B is a perspective view of the expansion housing 30 viewed from its back side.

As shown in FIGS. 1A and 1B, the disk array system 10 is formed by using a rack frame 11 as a base. Mount frames 12 are formed in a plurality of stages disposed in the upper and lower on the inside left and right side surfaces of the rack frame 11, so as to extend in the front/rear direction. The master housing 20 and expansion housings 30 are mounted by pullout along the mount frames 12. As shown in FIGS. 2A and 2B, boards or units for providing various functions for the disk array system 10 are attached to the master housing 20 and the expansion housings 30.

As shown in FIG. 2A, a plurality of disk drive units 52 each filled with a hard disk drive 51 are inserted in parallel into the front upper stage of the master housing 20. Each hard disk drive 51 is a hard disk drive having a communication interface for providing a communication function conforming to an FC-AL standard, an SCSI1 (Small Computer System Interface 1) standard, an SCSI2 standard, an SCSI3 standard, a parallel ATA (AT Attachment) standard, a serial ATA standard, or the like.

A battery unit 53, a display panel 54 for displaying the operating conditions etc. of the hard disk drives 51, and a flexible disk drive 55 are inserted into the front lower stage of the master housing 20. The battery unit 53 includes a secondary battery. The battery unit 53 has a function as a backup power supply for supplying power to boards or units when power supply from an AC/DC power supply 57 stops due to power failure or the like. The display panel 54 is provided with display devices such as LED lamps or the like for displaying the operating conditions etc. of the hard disk drives 51. The flexible disk drive 55 is used, for example, for loading a maintenance program.

As shown in FIG. 2B, power supply controller boards 56 are inserted onto the opposite side surfaces in the back upper stage of the master housing 20 one by one. Each power supply controller board 56 is connected to a plurality of hard disk drives 51 so as to be able to establish communications therewith. For example, the power supply controller board 56 and the plurality of hard disk drives 51 are connected to be able to establish communications through a loop-like communication path such as a communication path making communications in an FC-AL system (topology).

Each power supply controller board 56 is mounted with circuits for monitoring the condition of the AC/DC power supply 57, monitoring the conditions of the hard disk drives 51, controlling the power supply to the hard disk drives 51, controlling the cooling capacity of a cooling unit, controlling the display devices on the display panel 54, monitoring the temperature of each portion of the housing, and so on. Incidentally, the cooling unit is a unit for cooling the inside of the disk array system 10 or the inside of the housing 20 or 30. For example, the cooling unit is an intercooler, a heat sink, a cooling is fan of an air cooling type, or the like. The power supply controller board 56 is provided with a fiber channel cable connector 67, to which a fiber channel cable 91 is connected.

As shown in FIG. 2B, two AC/DC power supplies 57 are mounted in parallel in a space between the two power supply controller boards 56 in the back upper stage of the master housing 20. Each AC/DC power supply 57 supplies power to the hard disk drives 51, boards, units, etc. The AC/DC power supply 57 is connected to the power supply controller board 56 and set to be able to supply power to each hard disk drive 51 in accordance with a signal from the power supply controller board 56.

Incidentally, this embodiment is designed so that two power supply controller boards 56 and two AC/DC power supplies 57 are mounted redundantly in each of the master and expansion housings 20 and 30 in order to ensure security about the power supply to each housing 20, 30. However, one power supply controller board 56 and one AC/DC power supply 57 may be mounted in each housing 20, 30.

Each AC/DC power supply 57 is provided with a breaker switch 64 for turning on/off the output of the AC/DC power supply 57.

As shown in FIG. 2B, two air cooling fan units 58 are mounted in parallel under the AC/DC power supplies 57. Each cooling fan unit 58 is mounted with one or more cooling fans 66. The cooling fans 66 allow the air to flow into/from the housing to thereby discharge heat generated from the hard disk drives 51, the AC/DC power supplies 57, and so on, to the outside of the housing. Incidentally, vent pathways or vent holes for circulating the air through each master/expansion housing 20, 30 are formed in the housing 20, 30, and boards or units mounted thereon, so as to form a mechanism for discharging heat in the housing 20, 30 efficiently to the outside by the cooling fans 66. Although cooling fans 66 may be provided for each hard disk drive 51, it is preferable that larger cooling fans 66 are provided for each housing so that the number of chips or units can be reduced.

Each cooling fan unit 58 is connected to a controller board 59 or the power supply controller board 56 through a control line. The rotation number of each cooling fan 66 of the cooling fan unit 58 is controlled by the controller board 59 or the power supply controller board 56 through the control line.

As shown in FIG. 2B, one controller board 59 is inserted into the back lower stage of the master housing 20. The controller board 59 is mounted with a communication interface with the hard disk drives 51 mounted in the master housing 20 and the expansion housings 30, circuits for controlling the operations of the hard disk drives 51 (for example, controlling them in an RAID system) or monitoring the conditions of the hard disk drives 51, and so on.

Incidentally, although the power supply controller boards 56 control the power supply to the hard disk drives 51 or the cooling capacity of the cooling units in this embodiment, the controller board 59 may perform such control.

This embodiment adopts the mode in which the controller board 59 is mounted with a communication interface board 61 for providing a function of communication interface with an information processing apparatus 300, for example, a communication function conforming to an SCSI standard or a fiber channel standard, a cache memory 62 for storing data to be written into the hard disk drives 51 or data to be read therefrom, and so on. However, these functions may be mounted on another board.

The communication interface board 61 mounted on the controller board 59 is provided with an external connector 63 for making a connection to the information processing apparatus 300. The external connector 63 conforms to a predetermined interface standard such as SAN (Storage Area Network), LAN (Local Area Network) or SCSI built by a protocol such as fiber channel, Ethernet (registered trademark) or the like. The disk array system 10 is connected to the information processing apparatus 300 through a communication cable 92 connected to the connector 63.

Incidentally, two controller boards 59 may be mounted redundantly to ensure security about the control of the hard disk drives 51 in the master housing 20.

As shown in FIG. 3A, a plurality of disk drive units 52 receiving hard disk drives 51 are mounted in parallel on the front side of each expansion housing 30. As shown in FIG. 3B, power supply controller boards 56 are inserted onto the back opposite side surfaces of the expansion housing 30 one by one. In addition, two AC/DC power supplies 57 are mounted in parallel in a space between the two power supply controller boards 56. In addition, two cooling fan units 58 are mounted in parallel under the AC/DC power supplies 57. Each AC/DC power supply 57 is provided with a breaker switch 64 for turning on/off the power of the AC/DC power supply 57.

This embodiment is designed so that two power supply controller boards 56 and two AC/DC power supplies 57 are mounted redundantly in each expansion housing 30 in order to ensure security about the power supply to the expansion housing 30 as described above. However, one power supply controller board 56 and one AC/DC power supply 57 may be mounted in the expansion housing 30. Incidentally, the functions of the power supply controller boards 56 for controlling the power supply to the hard disk drives 51, controlling the cooling capacity of the cooling units, and so on, may be mounted on the controller board 59.

FIG. 4 shows an example of the configuration of each hard disk drive 51 received in each disk drive unit 52. The hard disk drive 51 has a housing 70; and magnetic disks 73, actuators 71, a spindle motor 72, heads 74 for reading/writing data, a mechanism control circuit 75 for controlling mechanism portions such as the heads 74 and the like, a signal processing circuit 76 for controlling a read/write signal of data from/to each magnetic disk 73, a communication interface circuit 77, an interface connector 79 for inputting/outputting various commands or data therethrough, and a power supply connector 80 which are all disposed in the housing 70. Incidentally, a cache memory for storing data temporarily is included in the communication interface circuit 77. Incidentally, the cache memory belonging to the hard disk drive 51 is referred to as disk cache in order to be distinguished from a cache memory 62 in a controller 500 which will be described later.

Each hard disk drive 51 is, for example, a storage unit provided with Contact Start Stop (CSS) type 3.5-inch magnetic disks, load/unload type 2.5-inch magnetic disks, or the like. For example, each 3.5-inch magnetic disk has a communication interface of SCSI1, SCSI2, SCSI3, FC-AL or the like. On the other hand, for example, each 2.5-inch magnetic disk has a communication interface of parallel ATA, serial ATA or the like.

When each 2.5-inch magnetic disk is received in the housing 20, 30 of the disk array system 10, it may be received in a vessel having a 3.5-inch shape. Thus, the shock resistance performance of the magnetic disks can be improved. Incidentally, the 2.5-inch magnetic disk and the 3.5-inch magnetic disk differ from each other not only in communication interface but also in I/O performance, power consumption, life, and so on. The 2.5-inch magnetic disk is inferior in I/O performance to the 3.5-inch magnetic disk, and the life of the former is shorter than that of the latter. However, the 2.5-inch magnetic disk is superior to the 3.5-inch magnetic disk in that the power consumption of the former is smaller than that of the latter.

Hardware Configuration of Disk Array System

FIG. 5 is a block diagram showing the hardware configuration of the disk array system 10 described as an embodiment of the invention.

As shown in FIG. 5, information processing apparatuses 300 are connected to the disk array system 10 through an SAN. The information processing apparatuses 300 are, for example, personal computers, work stations, mainframe computers, or the like.

The disk array system 10 has one master housing 20 and one or a plurality of expansion housings 30 as described previously. In this embodiment, the master housing 20 has controllers 500, hard disk drives 51, and so on. Each controller 500 has channel control portions 501, disk control portions 502, a CPU 503, a memory 504, a cache memory 62, a data controller 505, and so on. The controller 500 is mounted on the aforementioned controller board 59. On the other hand, each expansion housing 30 has hard disk drives 51 and so on. The hard disk drives 51 in the master and expansion housings are connected to the disk control portions 502 via an FC-AL 506 so as to be able to establish communication with the disk control portions 502. Incidentally, the connecting mode between each disk control portion 502 and each hard disk drive 51 will be described later in detail.

Each channel control portion 501 is an interface for making communication with the information processing apparatuses 300. The channel control portion 501 has a function of accepting a block access request in accordance with a fiber channel protocol.

Each disk control portion 502 is an interface for exchanging data with the hard disk drives 51 in accordance with an instruction from the CPU 503. The disk control portion 502 has a function of transmitting a data input/output request to the hard disk drives 51 in accordance with a protocol stetting down commands etc. for controlling the hard disk drives 51.

The CPU 503 administers the control of the disk array system 10 as a whole. The CPU 503 executes microprograms stored in the memory 504, so as to control the channel control portions 501, the disk control portions 502, the data controller 505, and so on. The microprograms include a data READ process 601, a data WRITE process 602 and the like as shown in FIG. 6.

The cache memory 62 serves to temporarily store data to be exchanged between each channel control portion 501 and each disk control portion 502.

The data controller 505 performs data transfer between each channel control portion 501 and the cache memory 62 or between the cache memory 62 and each disk control portion 502 under the control of the CPU 503.

Each controller 500 has a function of controlling the hard disk drives 51 under an RAID level (for example, 0, 1 or 5) conforming to a so-called RAID (Redundant Array of Inexpensive Disks) system. In the RAID system, a plurality of hard disk drives 51 are managed as one group (hereinafter referred to as RAID group). Logical volumes serving as access units from the information processing apparatuses 300 are formed on each RAID group. An identifier referred to as LUN (Logical Unit Number) is assigned to each logical volume. RAID configuration information is stored in the memory 504 in the form of an RAID configuration table 603 as shown in FIG. 6. The RAID configuration table 603 is referred to by the CPU 503 when the CPU 503 executes the data READ process 601 or the data WRITE process 602.

Incidentally, for example, the disk array system may be not a system designed as described above but a system serving as an NAS (Network Attached Storage) designed to accept a data input/output request based on file name designation from any one of the information processing apparatuses 300 in accordance with a protocol such as an NFS (Network File System).

Connecting Mode of Hard Disk Drives

Next, description will be made on the connecting mode between each controller 500 and each hard disk drive 51.

FIG. 7 shows a connecting mode between each disk control portion 502 and each fiber channel hard disk drive 51 stored in the master housing 20.

Each disk control portion 502 is connected to a plurality of hard disk drives 51 through an FC-AL 506. The FC-AL 506 has a plurality of PBCs (Port Bypass Circuits) 701. The fiber channel hard disk drives 51 are connected to the FC-AL 506 through the PBCs 701 respectively. Each PBC 701 is an electronic switch formed into a chip. The PBCs 701 also have a function of bypassing the disk control portions 502 or the hard disk drives 51 and thereby excluding them from the FC-AL 506 electrically. Specifically, when failures occur in some hard disk drives 51, the PBCs 701 separate the hard disk drives 51 from the FC-AL 506 so that communications can be established between any other hard disk drive 51 and each disk control portion 502.

In addition, the PBCs 701 allow the hard disk drives 51 to be removed and inserted while keeping the operation of the FC-AL 506. For example, when a new hard disk drive 51 is inserted, the hard disk drive 51 is incorporated into the FC-AL 506 so that communication can be established between the hard disk drive 51 and the disk control portion 502. Incidentally, a circuit board of the PBCs 701 may be provided on the rack frame 11 of the disk array system 10 or may be mounted partially or entirely on the controller board 59 or the power supply controller board 56.

FIG. 8 shows a connecting mode between each disk control portion 502 and each serial ATA hard disk drive 51 stored in the master housing 20.

Each hard disk drive 51 is connected to PBCs 602 of the FC-AL 506 through a converter 801. The converter 801 is a circuit for converting a fiber channel protocol and a serial ATA protocol into each other. The converter 801 is made of one chip in which a protocol converting function is incorporated. The converter 801 is provided in each disk drive unit 52.

FIG. 9 is another connecting mode in which serial ATA hard disk drives 51 are stored in the master housing 20.

Each converter 901 is a circuit for converting a fiber channel protocol and a serial ATA protocol into each other in the same manner as the converter 801 in FIG. 8. The converter 901 is connected to a PBC 602 of an FC-AL 506. A plurality of hard disk drives 51 are connected to each converter 901 through switches 902 respectively. The switches 902 are circuits for selecting one hard disk drive 51 with which communication should be established when the hard disk drives 51 are connected to a plurality of converters 901. Each switch 902 is provided in each disk drive unit 52. Each converter 901 is formed out of one chip or a plurality of circuits in which a protocol converting function is incorporated. For example, the converter 901 can be implemented by the configuration of an SATA master device disclosed in “U.S. Patent Application Publication No. 2003/0135577”. The converter 901 is mounted on the controller board 59, the power supply controller board 56 or the like.

Control for Enhancing Reliability

Description will be made on a method for enhancing reliability in reading from the hard disk drives 51 or in writing into the hard disk drives 51 in the disk array system 10 described above.

Parity Check in RAID Configuration

First, description will be made on a method for examining whether data stored in a hard disk drive 51 in the RAID configuration is in a false state or not. Here, the false state means a state where data is not written at a site specified by the disk control portion 502 and with contents specified likewise.

FIG. 10 shows a state where data are stored in the hard disk drives 51 in RAID-5. In RAID-5, an RAID group 1001 is formed out of a plurality of hard disk drives 51. In the example of FIG. 10, data A-D and parity data P(A-D) for detecting errors in the data A-D are stored in the hard disk drives 51. In the same manner, data E-H and parity data P(E-H) for the data E-H are stored. Such a combination of data and parity data is referred to as a stripe group 1002. In the RAID configuration having such strip groups 1002 formed therein, the controller 500 reading all the data and parity data of the strip group 1002 can examine whether the data are in a false state or not. First, in accordance with an instruction from the CPU 503, the disk control portion 502 reads the data A-D and the parity data P(A-D). Next, the CPU 503 performs parity check using the data A-D and the parity P(A-D). Thus, it can be examined whether any piece of the data A-D is in a false state or not.

When receiving a data read request from any one of the information processing apparatuses 300, the controller 500 may read all the data and parity data in a stripe group including the data to be read. Thus, the controller 500 can be prevented from reading false data from the hard disk drives 51 and transmitting the false data to the information processing apparatus 300. Incidentally, examining false data may be performed not at the time of receiving a data read request but at any desired timing. In such a manner, false data detection can be performed without giving any influence to the data reading performance.

In addition, using an update control table 1101 shown in FIG. 11, it is possible to examine whether data written in the hard disk drives 51 are in a false state or not. The update control table 1101 is constituted by drive numbers and sector numbers, and stored in the memory 504. In this embodiment, the sector numbers are defined by LBA (Logical Block Address), and managed by 128 LBA units as shown by LBA #1-128. Incidentally, the unit packaging the sector numbers is not limited to 128, but it may be any desired unit. When writing data into a hard disk drive 51 through the disk control portion 502, the CPU 503 changes the sector value of the hard disk drive 51 subjected to the writing, into “1” in the update control table 1101. The CPU 503 reads, through the disk control portion 502, all the data and parity data of a stripe group including the target sector of the hard disk drive 51 stored as “1” in the update control table 1101, and performs parity check. When the read data is not false, the CPU 503 changes the value of the sector in the update control table 1101 into “0”. Receiving a data read request from any one of the information processing apparatuses 300 through the channel control portion 501, the CPU 503 refers to the update control table 1101 and confirms whether a sector storing the data to be read has been examined or not. When the sector storing the data has not been examined, the CPU 503 examines data of a stripe group including the data to be read in accordance with the aforementioned procedure. In such a manner, examination upon data written into each hard disk drive 51 is performed before reception of a read request to read the data. Thus, the data reading performance can be prevented from lowering. In addition, incompletion of examination is stored in the update control table 1101, and parity check is performed when unexamined data is read. Thus, false data can be prevented from being read.

Examination of WRITE Data

Next, description will be made on a method for examining whether data is written correctly or not when the data is written into a hard disk drive 51.

FIG. 12 is a flow chart showing the control of the CPU 503 when the controller 500 writes data into a hard disk drive 51. Receiving a data write request from any one of the information processing apparatuses 300 through the channel control portion 501, the CPU 503 transmits to the disk control portion 502 an instruction to write the data into a hard disk drive 51 (S1201). Then, the CPU 503 transmits to the disk control portion an instruction to execute a seek process for moving the position of a head of a magnetic disk where the data has been written (S1202). Next, the CPU 503 reads the data from the cache memory 62 (S1203), and reads the data from the magnetic disk (S1204). The CPU 503 compares the data from the cache memory 62 and the data from the magnetic disk so as to examine whether they coincide with each other (S1205). When the two pieces of data do not coincide with each other, the CPU 503 informs the information processing apparatus 300 of the fact that writing has not been performed normally (S1206).

When the data stored in the magnetic disk is thus compared with the data stored in the cache memory 62, it is possible to confirm whether the data has been written in the magnetic disk correctly or not. In addition, even when the written data is in a false state, the data survives in the cache memory 62. Thus, there is no fear that the data is lost. Incidentally, when a head belonging to a hard disk drive having a magnetic disk is moved by a seek process or the like before data to be compared is read from the magnetic disk and from the cache memory 62, it is possible to prevent the head from reading twice in one and the same position when the position at the time of writing is false.

In the processing in FIG. 12, all the written data are read from the cache memory 62 and from the magnetic disk, and the two pieces of data are compared for examining the data. However, not all the data but a part of the data, for example, one segment at the head of the data and one segment at the end of the data may be read and compared. For example, large-size data (sequential data) are often written in serial ATA hard disk drives because they are used for applications such as data backup. In such a case, if data stored in a magnetic disk is compared with data stored in the cache memory 62 for all the written data, the performance in writing processing will be deteriorated conspicuously. In addition, when there occurs an error in writing position or the like when sequential data are written, it is highly likely that all the data are false. Therefore, in most cases, it can be judged whether the data are false or not if a part of the data is examined. That is, when comparison is performed upon a part of written data, for example, one segment at the head of the data and one segment at the end of the data, it is possible to check false data while preventing the performance in writing processing from being deteriorated.

Alternatively, the method for examining data written in the hard disk drive 51 may be changed in accordance with the size of the data. FIG. 13 is a flow chart showing the processing for changing the examination method in accordance with whether the written data is sequential data or not. The CPU 503 transmits to the disk control portion 502 an instruction to write data into a hard disk drive 51 (S1301). Then, the CPU 503 transmits to the disk control portion an instruction to execute a seek process for moving the position of the head of the magnetic disk where the data has been written (S1302). The CPU 503 judges whether the data is sequential data or not (S1303). Incidentally, the judgment as to whether the data is sequential data or not is performed based on whether the size of the written data reaches a predetermined size or not.

When the data is sequential data, the CPU 503 reads one segment at the head of the data and one segment at the end of the data from the cache memory 62 and from the magnetic disk. On the contrary, when the data is not sequential data, the CPU 503 reads all the data from the cache memory 62 and from the magnetic disk (S1306 and S1307). After that, the CPU 503 compares the two pieces of read data with each other and examines whether they coincide with each other (S1308). When they do not coincide, the CPU 503 informs the information processing apparatus 300 of the fact that writing has not been performed normally (S1309).

When the written data is sequential data, comparison as to a part of the data is made between data stored in the magnetic disk and data stored in the cache memory 62 in such a manner. Thus, it is possible to detect data falseness while suppressing the lowering of the performance in writing processing. On the contrary, when the written data is not sequential data, comparison as to all the written data is made between data stored in the magnetic disk and data stored in the cache memory 62. Thus, it is possible to detect data falseness perfectly without lowering the performance in writing processing as conspicuously as in the case of sequential data.

In order to improve the performance in writing data, each hard disk drive 51 may have a function as follows. That is, when receiving a data write request from the controller 500, the hard disk drive 51 writes the data only into the disk cache, and informs the controller 500 of the completion of writing. In this case, the written data cannot be examined in the method described in FIGS. 12 and 13. FIG. 14 is a flow chart of processing for examining written data when the hard disk drive 51 has such a function. The CPU 503 monitors the hard disk drive 51 as to whether the number of times of writing into the hard disk drive 51 has exceeded a predetermined number or not (S1401). When it exceeds the predetermined number, the CPU 503 gives the hard disk drive through the disk control portion 502 an instruction to write the data stored in the disk cache into a magnetic disk (S1402). Then, the CPU 503 reads the data from the cache memory 62 and from the magnetic disk (S1403 and S1404). The CPU 503 confirms whether the data from the cache memory 62 and the data from the magnetic disk coincide with each other or not (S1405). When they do not coincide, the CPU 503 informs the information processing apparatus 300 of the fact that writing has not been performed normally (S1406). Thus, data falseness can be detected in spite of use of the aforementioned function of enhancing the performance in writing processing. Incidentally, in the processing in FIG. 14, data written into the magnetic disk and data written into the cache memory are compared when the number of times of writing exceeds a predetermined number. However, the examination may be made whenever a predetermined time has passed or whenever the disk cache has no free space.

In the case of a serial ATA hard disk drive 51, data is often written incorrectly due to a failure of its head. Therefore, description will be made on a method for detecting a failure of a head of a hard disk drive 51 when data is read from the hard disk drive 51.

FIG. 15 is a diagram showing a head check control table 1501. The head check control table 1501 is constituted by drive numbers, head numbers and sector numbers, and stored in the memory 504. Each sector number is defined by LBA in the same manner as in the update control table 1101. When data is written into the hard disk drive 51 through the disk control portion 502, the CPU 503 changes the value of “existence of update” of the sector of the head with which the data was written, into “1” in the head check control table 1501.

FIG. 16 is a flow chart of the head check processing to be executed by the CPU 503. The CPU 503 sets 1 as the initial value of an examination head number (S1601). The CPU 503 waits a predetermined time (S1602), and writes examination data into a control block of a magnetic disk using a head specified by the examination head number (S1603). Incidentally, the control block is a predetermined storage area on the magnetic disk. Next, the CPU 503 reads the data written in the control block (S1604), and confirms whether the read data and the examination data coincide with each other or not (S1605).

When the two pieces of data coincide with each other, the CPU 503 concludes that there is no abnormality in the head, and changes the value of “existence of update” of the head into “0” in the head check control table 1501 (S1606). The CPU 503 adds 1 to the examination head number (S1607). The CPU 503 confirms whether the examination head number is larger than a maximum value of the head number or not (S1608). When the examination head number is larger, the CPU 503 sets 1 as the examination head number. The CPU 503 executes the head check processing upon the set head number repeatedly.

When the data read from the control block does not coincide with the examination data, the CPU 503 informs the information processing apparatus 300 of the fact that there occurs an abnormality in the hard disk drive 51 in question, and then terminates the processing.

FIG. 17 is a flow chart of processing when the CPU 503 receives a data read request from any one of the information processing apparatuses 300. The CPU 503 receives a data read request from the information processing apparatus 300 through the channel control portion 501 (S1701). The CPU 503 confirms the value of “existence of update” of a target sector of a hard disk drive 51 where the data is stored in the head check control table 1501 (S1702 and S1703). The “existence of update” whose value is “1” indicates the state where the aforementioned head check processing has not been performed though data writing has been performed on the LBA of the hard disk drive 51 in question. When the value of “existence of update” is “0”, the CPU 503 reads the data from the hard disk drive 51 (S1708).

When the value of “existence of update” is “1”, the CPU 503 writes examination data into a control block of a magnetic disk using the head in question in the same manner as in the aforementioned head check processing (S1704). Incidentally, the control block is a predetermined storage area on the magnetic disk. Next, the CPU 503 reads the data written in the control block (S1705), and confirms whether the read data coincides with the examination data or not (S1706).

When the two pieces of data coincide with each other, the CPU 503 concludes that there is no abnormality in the head, and changes the value of “existence of update” of the head into “0” in the head check control table 1501 (S1707). Then, the CPU 503 reads the requested data from the hard disk drive 51 in accordance with the read request (S1708).

When the data read from the control block does not coincide with the examination data, the CPU 503 notifies the information processing apparatus 300 of the fact that there occurs an abnormality in the hard disk drive 51 in question (S1709), and then the CPU 503 terminates the processing without reading the data from the hard disk drive 51.

In such a manner, when data written in the hard disk drive 51 is read, it is possible to confirm whether the head with which the data was written is normal or not. When the head is abnormal, there is a possibility that the data is not written correctly or there is a possibility that the data cannot be read correctly. By detecting abnormality in the head when data is read, it is possible to prevent false data from being read.

Examination Based on Parity Assignment

According to the aforementioned method in which all the data of a stripe group in the RAID configuration are read and subjected to parity check, it is not possible to determine which data of the stripe group is in a false state. It is indeed possible to prevent false data from being read, but it is not possible to restore the false data. Thus, the data may be lost. Therefore, description will be made on a method for assigning parity data to each piece of data separately from parity data in the stripe group.

The CPU 503 generates parity data for detecting errors for a plurality of sectors serving as a minimal unit with which data is written into each hard disk drive 51. In this embodiment, a combination of data and parity data for such a plurality of sectors is referred to as data unit. Receiving a data write request from any one of the information processing apparatuses 300 through the channel control portion 501, the CPU 503 forms a data unit from the data to be written. The CPU 503 writes the data unit into the hard disk drive 51 through the disk control unit 502.

FIG. 18 is a diagram showing the state where one piece of data 1801 is written in a hard disk drive. The data 1801 is constituted by a plurality of sectors S#1 to S#4, and a data unit 1803 is formed out of the data 1801 and parity data 1802 for the data 1801 of the plurality of sectors. Receiving a data read request from any one of the information processing apparatuses 300 through the channel control portion 501, the CPU 503 reads the data unit 1803 of the requested data through the disk control portion 502, and performs parity check on the data so as to examine whether the data is in a false state or not. In such a manner, by reading only the data to be read in response to the read request, it is possible to judge whether the data is in a false state or not. In addition, when the hard disk drives 51 have a redundant RAID configuration as RAID 5, the data can be restored using other data and parity data in the stripe group. Thus, there is no fear that the data is lost.

When there occurs a failure of a head or the like in one hard disk drive 51, it is highly likely that there appear a plurality of false sectors. Assume that a plurality of sectors of the data unit 1803 become false when the data unit 1803 is written into one hard disk drive 51. In such an event, there is a case where falseness cannot be detected by parity check.

Therefore, as shown in FIG. 19, the CPU 503 may write and distribute the data unit 1803 among a plurality of hard disk drives 51 in the RAID group through the disk control portion 502. FIG. 20 is a diagram showing a data unit control table 2001. The data unit control table 2001 shows the correspondence of data units 1803 each constituted by a plurality of sectors to LBAs of hard disk drives 51. The example of FIG. 20 shows that one data unit 1803 formed out of 130 sectors 000-129 is constituted by LBAs 000-064 of hard disk drives 51 whose drive numbers are #0 and #1. Receiving a data write request from any one of the information processing apparatuses 300, the CPU 503 refers to the data unit control table 2001, and writes and distributes each data unit 1803 of the requested data among a plurality of hard disk drives 51.

Thus, even when there occurs a failure in one hard disk drive, it is possible to increase the probability that falseness of data can be detected.

Environment of Mixture of Fiber Channel and Serial ATA

Next, description will be made on the disk array system 10 in which fiber channel hard disk drives 51 and serial ATA hard disk drives 51 are mixed.

FIG. 21 is a block diagram showing a disk array system in which fiber channel hard disk drives 51 are received in a first housing 2101 and serial ATA hard disk drives 51 are received in a second housing 2102. Incidentally, the first and second housings 2101 and 2102 correspond to the master housing 20 and the expansion housing 30 respectively. Each hard disk drive 51 is connected with the disk control portion 502 in the mode described previously. In addition, FIG. 19 shows a mode in which a plurality of serial ATA hard disk drives are connected to one converter 901. However, each serial ATA hard disk drive may be connected through a converter 801 provided for each disk drive unit as described previously.

In the disk array system 10 configured thus, it is requested to enhance the reliability of the serial ATA hard disk drives 51 whose reliability is lower than that of the fiber channel hard disk drives 51. Therefore, the controller 500 applies the aforementioned method for enhancing the reliability only to the serial ATA hard disk drives 51. Thus, the reliability in reading/writing data from/into the serial ATA hard disk drives 51 can be enhanced without lowering the performance in reading/writing data from/into the fiber channel hard disk drives 51 used for processing such as essential work requested to have high access performance. In addition, it is not necessary to change the physical structure, for example, to provide two heads for each magnetic disk of each serial ATA hard disk drive 51. It is therefore possible to suppress the manufacturing cost of the serial ATA hard disk drives 51.

Incidentally, in this embodiment, the fiber channel hard disk drives 51 and the serial ATA hard disk drives 51 are mixed. However, other hard disk drives 51 may be used if they conform to interface standards different in reliability. For example, the serial ATA hard disk drives 51 may be replaced by parallel ATA hard disk drives 51.

The embodiments have been described above in order to make the present invention understood easily. The invention should not be interpreted to be limited to the embodiments. The invention can be changed or modified without departing from its scope and spirit. Any equivalent to the invention is also included therein. In addition, Japanese Patent Application No. 2003-400517 applied in Japan Patent Office on Nov. 28, 2003 is cited to support the present invention and the disclosure of which is incorporated herein by reference. 

1. A storage system, comprising: a controller controlling to write data to a plurality of storage regions and to read data from said storage regions; and a plurality of disk drives coupled to said controller having said storage regions, wherein said controller compares contents corresponding to data written to a storage region of said storage regions in said storage regions and data read from said storage region, said contents being stored in said controller until said comparison at the earliest, after receiving a write request in said controller.
 2. A storage system according to claim 1, wherein said controller implements said comparison for preventing to write data to another address which is different from an address specified by said controller.
 3. A storage system according to claim 1, wherein said controller implements said comparison for preventing to write data of another contents which are different from contents specified by said controller.
 4. A storage system according to claim 1, wherein said controller controls to move a head in one of said disk drives from said storage region to another storage region before a step of said read from said storage region so that said controller is able to check whether data are written in said storage region specified by said controller or not.
 5. A storage system according to claim 1, wherein said controller compares contents corresponding to a part of data written to said storage region and a part of data read from said storage region.
 6. A storage system according to claim 1, wherein said controller compares contents corresponding to segments at head and at end of data written to said storage region and segments at head and at end of data read from said storage region.
 7. A storage system according to claim 1, wherein said controller implements one of comparisons which are a first comparison which is to compare contents corresponding to all of data written to said storage region and all of data read from said storage region, and wherein a second comparison which is to compare contents corresponding to a part of data written to said storage region and a part of data read from said storage region.
 8. A storage system according to claim 1, wherein said controller notices to an information unit, said information unit coupled to said controller and transferring a read request or said write request to said controller, that said contents is not corresponding to said data read from said storage region in case of that said contents is not corresponding to said data read from said storage region.
 9. A storage system according to claim 1, wherein said controller processes said write request by using data stored in said controller in case of that said contents is not corresponding to said data read from said storage region.
 10. A storage system according to claim 1, wherein said controller prevents to transfer said data written to said storage region to an information unit, said information unit coupled to said controller and transferring a read request or said write request to said controller, in case of that said contents is not corresponding to said data read from said storage region.
 11. A storage system according to claim 1, further comprising: a cache memory, in said controller, used to store data transferred from an information unit, said information unit coupled to said controller and transferring a read request or said write request to said controller, and data read from said storage regions, and wherein said contents are stored in said cache memory until said comparison at the earliest.
 12. A storage system, comprising: a controller controlling to write data to a plurality of storage regions and to read data from said storage regions; and a plurality of disk drive units coupled to said controller having a plurality of disk drives corresponding to said storage regions and having a memory which temporarily store data from said controller to said disk drives, one of said disk drive units replies to said controller according to storing data to said memory, wherein said controller controls said one of said disk drive units to write data stored in said memory in one of said disk drive units to a storage region of said storage regions in said one of disk drive units and compares contents corresponding to said data written to said storage region and data read from said storage region, said contents are stored in said controller until said comparison at the earliest.
 13. A storage system according to claim 12, wherein said controller controls said one of said disk drive units to write a plurality of data stored in said memory to said storage region.
 14. A storage system according to claim 12, wherein said controller controls said one of said disk drive units to write data stored in said memory to said storage region according to the number of times of writing data from said controller to said memory.
 15. A storage system according to claim 12, wherein said controller controls said one of said disk drive units to write data stored in said memory to said storage region as predetermined time has passed.
 16. A storage system according to claim 12, wherein said controller controls said one of said disk drive units to write data stored in said memory to said storage region according to amount of free space in said memory.
 17. A storage system according to claim 12, wherein said controller notices to an information unit, said information unit coupled to said controller and transferring a read request or a write request to said controller, that said contents is not corresponding to said data read from said storage region in case of that said contents is not corresponding to said data read from said storage region.
 18. A storage system according to claim 12, wherein said controller processes a write request by using data stored in said controller in case of that said contents is not corresponding to said data read from said storage region.
 19. A storage system according to claim 12, wherein said controller prevents to transfer said data written to said storage region to an information unit, said information unit coupled to said controller and transferring a read request or a write request to said controller, in case of that said contents is not corresponding to said data read from said storage region.
 20. A storage system according to claim 12, further comprising: a cache memory, in said controller, used to store data transferred from an information unit, said information unit coupled to said controller and transferring a read request or said write request to said controller, and data read from said storage regions, wherein said contents are stored in said cache memory until said comparison at the earliest. 